# 
# This file contains the version information used to feed the app's About box,
# as well as the version contained in the os-specific executable
#
# ONLY EDIT THESE ONE AS "RELEASES" ARE MADE
# See below for more information
#

[numbers]
major=2
minor=1
build=1
modifier: 

[text]
name=Levelator

# A versioning policy, borrowed from RubyGems:
 
#    * Versions shall be represented by three non#negative integers, separated by periods (e.g. 3.1.4). The first integers is the '''major''' version number, the second integer is the '''minor''' version number, and the third integer is the '''build''' number.
#
#    * A category 1 change (implementation detail) will increment the build number.
#
#    * A category 2 change (backwards compatible) will increment the minor version number and reset the build number.
#
#    * A category 3 change (incompatible) will increment the major build number and reset the minor and build numbers.
#
#    * Any ''public'' release of a gem should have a different version. Normally that means incrementing the build number. This means a developer can generate builds all day long for himself, but as soon as he/she makes a public release, the version must be updated.
#
#Examples of Category 1 changes:
#
#    * Switch from an array based implementation to a linked#list based implementation.
#    * Provide an automatic (and transparent) backing store for large stacks.
#
#Examples of Category 2 changes might be:
#
#    * Add a depth method to return the current depth of the stack.
#    * Add a top method that returns the current top of stack (without changing the stack).
#    * Change push so that it returns the item pushed (previously it had no usable return value).
#
#Examples of Category 3 changes might be:
#
#    * Changes pop so that it no longer returns a value (you must use top to get the top of the stack).
#    * Rename the methods to push_item and pop_item.
#
#
#"""
